fix(mcp-registry): retire legacy staging endpoint, align scopes, add smithery manifest#2
Merged
BarisSozen merged 1 commit intomainfrom Apr 22, 2026
Merged
Conversation
…smithery manifest - mcp-registry.json: drop legacy staging endpoint default (142.93.106.129 — no longer operational) in favor of canonical https://hashlock.markets/api/graphql. Fix npm scope to @hashlock-tech/mcp (matches published package and package.json); correct vendor to Hashlock-Tech; add Sui to supported-chains string; update homepage to hashlock.markets; clarify SIWE 7-day JWT. - smithery.yaml: add Smithery.ai manifest. Registry namespace io.github.Hashlock-Tech/hashlock matches mcpName in package.json. JWT TTL 7 days to match README and web/public/llms-full.txt.
BarisSozen
force-pushed
the
fix/mcp-registry-hardening
branch
from
4241d2a to
a1eb2da
Compare
BarisSozen
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Public MCP metadata hardening. No runtime behavior change in the
published server; fixes stale/incorrect registry metadata and adds a
Smithery manifest for discovery.
Changes
operational) in favor of the canonical production endpoint
https://hashlock.markets/api/graphql.
and package.json); same for installation.command.
(SIWE, 7-day TTL).
mcpName in package.json.
web/public/llms-full.txt).
Out of scope (explicitly not touched)
@hashlock-tech/sdk here; the agent-principal test block from
68bbedf is preserved.
is present, CI is green.
sconfig.json.
Verification
node -e "JSON.parse(fs.readFileSync('mcp-registry.json'))": passes.python -c "import yaml; yaml.safe_load(open('smithery.yaml'))": passes.HashLock Tech, @hashlock/mcp.
Status
Held as draft until
https://hashlock.markets/api/graphqlisserving 200 from the canonical gateway (currently returning 502). Lift
draft + merge once the endpoint is live so consumers installing 0.1.8
get a working default.
Rollout
Merge → next
npm publish(0.1.8) picks up the mcp-registry changes.smithery.yamlis picked up by Smithery crawlers independently. Nobreaking changes for existing consumers (canonical
@hashlock-tech/...scope was already the published one).